User documentation of the development environment, version 3.24.0

Content of this user documentation

This user documentation is on the development environment Neuron Power Engineer that is a tool by Neuron for programming a wide variety of →PLCs (Programmable Logic Controllers). Neuron Power Engineer provides comfortable editors for the IEC programming languages →ST (Structured Text) and →FBD (Function Block Diagram).

Development environment and IEC 61131-3
It is possible to create applications in Neuron Power Engineer according to the industry standard IEC 61131-3. In this case, knowledge about this IEC-standard is essential (see glossary item →IEC 61131-3 for links to sources).

This user documentation is valid for Neuron Power Engineer version 3.24.0.

Where to start	Details to know
Installation instructions Tutorials The dos and don'ts when working Release notes: Release notes for version Release notes for system libraries	Reference documentation with information about the following →features: Basic actions in the development environment Project explorer to manage project and Application navigator as an alternative to the project explorer Creating application in ST-editor Creating the interface in the interface editor System blocks for the application Testing, debugging and tracing the application Instance-related and PLC-related information and actions within Instances view Browsing to the objects of the application by using the Object Browser view Output messages More features might be provided in your used Neuron Power Engineer product version. PLC-specifications within editor for PLC-object System data types for the application Hardware configuration The following features are not provided in all variants of Neuron Power Engineer: Concept Information Accessing hardware IOs via EC-Master and EC-Engineer of Acontis Checking the identity and integrity of artifacts Command line interfaces Creating application in C or C++ Creating application in FBD-editor Creating application in LD-editor Creating custom library with user blocks Hardware parameterization using the safety parameter editor Local variants or copies for library elements Migration Preparing the hardware parameterization by the safety parameter editor Teaming up to create applications Testing single POUs by using the test framework Validating an application Visualization for application
Good to know	Legal information
IEC-compliance Keyboard shortcuts Troubleshooting and FAQ Glossary	Copyright notes License agreement for IDE Contact information

Where to start

Details to know

Installation instructions

Tutorials

The dos and don'ts when working

Release notes:

Reference documentation with information about the following →features:

More features might be provided in your used Neuron Power Engineer product version.

The following features are not provided in all variants of Neuron Power Engineer:

Concept Information

Accessing hardware IOs via EC-Master and EC-Engineer of Acontis

Checking the identity and integrity of artifacts

Command line interfaces

Creating application in C or C++

Creating application in FBD-editor

Creating application in LD-editor

Creating custom library with user blocks

Hardware parameterization using the safety parameter editor

Local variants or copies for library elements

Migration

Preparing the hardware parameterization by the safety parameter editor

Teaming up to create applications

Testing single POUs by using the test framework

Validating an application

Visualization for application

Good to know

Legal information

IEC-compliance

Keyboard shortcuts

Troubleshooting and FAQ

Glossary

License agreement for IDE

Contact information

Getting support and help

If you cannot find the requested information in this user documentation at all, contact the support team of Neuron.

Up-to-date information within online-version

Please check the online-version (provided under https://help.neuron-automation.eu) whether new pieces of information have been added since this user manual (as PDF/HTML/Word) has been published; e.g. the release notes quote new problems or there are new articles in the troubleshooting- or FAQ-section.
The online-version of the release notes for Neuron Power Engineer is available under: https://help.neuron-automation.eu – Use the version picker (above the table of contents) to switch to the relevant version of Neuron Power Engineer.

Typographical conventions

The following conventions are applied within this documentation in the interest of improving readability:

Bold	names of commands, buttons etc. within Neuron Power Engineer and/or emphasizing important text passages Example: menu File, button Finish
Italics	variable information in a term Example: logiRTS_Vx.y.z_name.tar.gz → x.y.z and name are examples of variable information.
`Monospace`	files/folders, user input or output of Neuron Power Engineer Example: ST-Code `up : BOOL;`
→term	reference to glossary item Example: →target system Usually, the reference is given at first occurrence of the term in the article.

Hints in this documentation are presented as follows:

Title of a warning

This is a warning that the reader/user must know/observe for fault prevention and/or detection. This hint is used for restrictions, limitations, deviations or similar.

Title of a note

This is a note that the reader/user should be aware of. This hint is used for important information. Knowing the note helps to avoid problems during an operation.

In addition, the symbol (warning) is used to indicate important information. The symbol is usually used in paragraphs, bulleted lists and/or numbered lists.

Title of an information

This is a piece of information that the reader/user should know. This hint is used for helpful information that helps the user to understand the operation (e.g. of a function).

In addition, the symbol is used to indicate helpful information. The symbol is usually used in paragraphs, bulleted lists and/or numbered lists.

Good to know
This is a piece of background information about the current function or information pointing out additional functions/features in the context of the current function. Usually. such a piece of information appears at the end of a description or after a bulleted or numbered list.